Method and Apparatus for Implementing a Predetermined Operation in Device Management

ABSTRACT

A method for implementing a predetermined operation in device management, being based on a DM system defined by OMA, includes: sending by the device management system a second predetermined operation based on a trigger condition to a terminal device and storing by the terminal device the received second predetermined operation; and obtaining by the terminal device from itself the second predetermined operation and executing the second predetermined operation when the trigger condition is satisfied. The present invention also discloses an apparatus for implementing a predetermined operation in device management.

This application is a continuation of U.S. patent application Ser. No.12/004,048, filed on Dec. 20, 2007, which is a continuation ofInternational Application No. PCT/CN2006/001449, filed on Jun. 26, 2006,which claims priority to Chinese Patent Application No. 200510080257.3,filed on Jun. 30, 2005, all of which are hereby incorporated byreference in their entities.

TECHNICAL FIELD

The present invention relates to device management technologies in thecommunication field, and more particularly to a method and an apparatusfor implementing a predetermined operation in device management.

BACKGROUND

Mobile terminals are an important part in the whole mobile operating andserving system. With the more and more complex terminal functions, theprobability that problems occur in software of the terminals increasesprominently. As the competition between operators will become fiercerand fiercer in the future, how to effectively assure users' experience,improve users' loyalty, and keep efficient quality of service andlow-cost device maintenance has become an important concern for theoperators and terminal vendors.

An event trigger mechanism has been defined in an existing Open MobileAlliance Device Management (OMA DM) specification, which is mainly usedin the case that when a Device Management (DM) service delivers adiagnosing or fault reporting task and then a terminal makes a diagnosisor a fault occurs, the terminal sends a diagnostic result or faultreports collected by the terminal back to the server. This event triggermechanism is limited to the reporting of diagnostic result or faultreports from the terminal to the server, but the terminal does not carryout any other operations.

In an existing solution, an approach of Trap Management Object (Trap MO)is provided for diagnosis and fault tracking and reporting running onthe terminal. This Trap MO provides two kinds of trigger mechanisms,i.e. time-based trigger mechanism and event-based trigger mechanism.When a device management server delivers a diagnosing or fault trackingoperation, the operation is delivered in a form of a Trap MO and theTrap MO contains parameters related to the diagnosing or faultreporting. After collecting the diagnostic data or fault reports, a DMagent reports the collected diagnostic data or fault reports to the DMserver upon the occurrence of a trigger condition. FIG. 1 shows aspecific processing procedure.

In process 1, the DM server delivers a diagnosing or fault trackingoperation in a form of a Trap MO.

In process 2, the DM agent in a terminal device collects diagnostic dataor fault reports.

In process 3, the trigger condition occurs, and the DM agent executes atriggered operation.

In process 4, the DM agent sends the diagnostic data or fault trackingreports to the DM server.

The format of a Trap MO provided in the existing OMA DM protocol isshown in FIG. 2.

In this figure, TrapID is a unique identifier identifying the Trap MO.

The leaf node CM indicates data collection policies for the Trap MO.

The leaf node Result stores diagnostic data or fault reports to bereported to the DM server.

The leaf node ServerID identifies the DM server to which the DM agentwill send diagnostic data or fault tracking reports

The leaf node Enable acts as a switch of a Trap for controlling whetherto enable the Trap.

Reporting/Type is adapted to indicate whether the Trap MO is time(TM)-triggered or event (EV)-triggered.

The value of the leaf node Reporting/Value is adapted to, if the Trap MOis time-triggered, indicate the interval at which the collecteddiagnostic data or fault reports are sent to the server, or if the TrapMO is event-triggered, indicate how many times the event occurs when thediagnostic data or fault reports are sent to the server.

TrapRef corresponds to other Trap MOs that may be referenced by thisTrap MO, and a TrapRef is used here to refer to the referenced Trap MO.

Although the existing OMA DM trigger mechanism provides the twodifferent mechanisms, time-based trigger mechanism and event-basedtrigger mechanism, it has drawbacks as follows.

1. The function performed by the terminal is limited to the reporting tothe server when the trigger condition is satisfied, resulting in greatlimitation in application.

2. It is impossible to recover from the failure or make a backupautomatically when an abnormal condition such as a failure or a faultoccurs on the terminal.

SUMMARY OF THE INVENTION

The present invention provides a method and an apparatus forimplementing a predetermined operation in device management, so as toaddress the limitation in the prior art that the terminal deviceperforms only the reporting operation.

The technical solutions for implementing the present invention aredescribed as follows.

A method for implementing a predetermined operation in devicemanagement, being based on a Device Management (DM) system defined byOpen Mobile Alliance (OMA), includes: sending a second predeterminedoperation based on a trigger condition to a terminal device and storingthe received second predetermined operation; and obtaining from theterminal device the second predetermined operation and executing thesecond predetermined operation when the trigger condition is satisfied.

Optionally, the storing the received second predetermined operationincludes: storing the received second predetermined operation into aTrap management object in a form of an executable node; and theobtaining the second predetermined operation and executing the secondpredetermined operation includes: obtaining the executable node from theTrap management object and executing the second predetermined operation.

Optionally, the storing the received second predetermined operationincludes: storing a path name of an executable script file for thereceived second predetermined operation into a leaf node in a Trapmanagement object; and the obtaining the second predetermined operationand executing the second predetermined operation includes: obtaining thepath name of the executable script file from the leaf node and executingthe script file directed by the path name so as to execute the secondpredetermined operation.

Optionally, the storing the received second predetermined operationdevice includes: storing the received second predetermined operationinto a leaf node in a Trap management object in a form of extensiblemarkup language; and the obtaining the second predetermined operationand executing the second predetermined operation includes: obtaining avalue of the leaf node and making an extensible markup language parsing,and executing the second predetermined operation.

Optionally, the storing the received second predetermined operationincludes: storing the received second predetermined operation into aleaf node in a Trap management object in a form of a uniform resourceidentifier; and the obtaining the second predetermined operation andexecuting the second predetermined operation includes: reading theuniform resource identifier from the leaf node and obtaining amanagement object corresponding to the uniform resource identifier, andexecuting an operation of the management object so as to execute thesecond predetermined operation.

Optionally, the storing the received second predetermined operationincludes: storing the received second predetermined operation into aleaf node in a Trap management object in a form of a uniquepredetermined operation identifier; and the obtaining the secondpredetermined operation and executing the second predetermined operationincludes: obtaining the unique predetermined operation identifier fromthe leaf node and executing an operation directed by the uniquepredetermined operation identifier so as to execute the secondpredetermined operation.

Optionally, the second predetermined operation is stored in a Trapmanagement object in a form of an executable node.

Optionally, the second predetermined operation is presented in a form ofa tree structure or an executable node, and is associated with a Trapmanagement object in the terminal device by means of a predefinedassociation identifier; and the second predetermined operation and theassociation identifier belong to a same parent node.

Optionally, the second predetermined operation is presented in a form ofa tree structure, and is associated with a Trap management object in theterminal device by means of a predefined association identifier; and theassociation identifier is located in a node on a tree where the secondpredetermined operation resides.

Optionally, the predefined association identifier is a unique identifierTrapID of the Trap management object in the terminal device.

Optionally, the second predetermined operation includes maintenanceprocessing to be implemented.

Optionally, the maintenance processing includes failure repair and/ordata backup.

Optionally, the method further includes reporting a result of the secondpredetermined operation to the device management server after executingthe second predetermined operation.

Optionally, when the trigger condition occurs, the method furtherincludes executing a first predetermined operation.

Optionally, the first predetermined operation includes reportingdiagnostic and/or fault information to a device management server.

Optionally, the trigger condition includes event trigger condition andtime trigger condition.

An apparatus for implementing a predetermined operation in devicemanagement, being applicable to a terminal device, wherein the apparatusincludes a predetermined operation receiving module, a predeterminedoperation executing module and a monitoring module, and wherein thepredetermined operation receiving module is adapted to receive a secondpredetermined operation based on a trigger condition sent by a devicemanagement server and store the second predetermined operation based onthe trigger condition into the storing module; the monitoring module isadapted to monitor whether the trigger condition is satisfied and notifythe predetermined operation executing module when the trigger conditionis satisfied; and the predetermined operation executing module isadapted to obtain and execute the second predetermined operation fromthe storing module according to a received notification.

Optionally, the apparatus further includes a storing module adapted tostore the second predetermined operation and the trigger condition.Optionally, the predetermined operation receiving module is furtheradapted to receive a first predetermined operation based on a triggercondition sent from the device management server and storing the firstpredetermined operation based on the trigger condition into the storingmodule; the storing module is further adapted to store the firstpredetermined operation; and the predetermined operation executingmodule is further adapted to obtain the first predetermined operationfrom the storing module and execute the obtained first predeterminedoperation according to a received notification.

A method for implementing a predetermined operation in device managementin a terminal device, being based on a device management system definedby Open Mobile Alliance, wherein the method includes: receiving a secondpredetermined operation based on a trigger condition and storing thereceived second predetermined operation; and obtaining the secondpredetermined operation and executing the second predetermined operationwhen the trigger condition is satisfied.

The present invention provides the advantages as follows. 1. Functionmechanism of a MO is extended so that operations for different functionsmay be triggered to be executed upon the occurrence of the triggercondition. Especially for function mechanism of a Trap MO, the terminaldevice is not limited to the function of reporting diagnostic data andfault reports to the DM server.

2. When the terminal device cannot operate normally due to a failure ora fault, the terminal device can execute a predetermined operationdelivered from the DM server so as to recover from the abnormalcondition, thereby providing a fault tolerance mechanism.

3. By applying the present invention based on the above fault tolerancemechanism, the workload for the operator to maintain terminals may bereduced and the terminal devices may recover from abnormal conditionstimely, thereby improving the users' loyalty.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow chart illustrating the fault reporting in the priorart.

FIG. 2 is a schematic diagram illustrating the format of a Trap MOspecified in the OMA DM specification in the prior art.

FIGS. 3A, 3B, 3C, 3D and 3E are schematic diagrams illustrating thepresenting of a predetermined operation on a management tree of a deviceaccording to an embodiment of the present invention.

FIGS. 4A, 4B and 4C are schematic construction diagrams illustrating apredetermined operation according to an embodiment of the presentinvention.

FIGS. 5 and 6 are flow charts illustrating the implementing of a faultevent-triggered or time-triggered predetermined operation according toan embodiment of the present invention.

FIG. 7 is a schematic structure diagram illustrating an apparatusaccording to an embodiment of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

A key principle of the present invention lies in that a devicemanagement server sends a second predetermined operation based on atrigger condition to a terminal device, the terminal device stores thereceived second predetermined operation, and the terminal device obtainsfrom itself and executes the second predetermined operation. The secondpredetermined operation includes but is not limited to maintenanceprocessing to be implemented locally by the terminal device, such asfailure repair and/or data backup. The terminal device may report aresult of the second predetermined operation to the device managementserver after implementing the second predetermined operation. Thetrigger condition mentioned above includes but is not limited to anevent trigger condition or a time trigger condition.

In addition, the terminal device may further execute a firstpredetermined operation. The first predetermined operation includes butis not limited to reporting of diagnostic and/or fault information bythe terminal device to the device management server.

In this way, when a failure or fault occurs, not only the firstpredetermined operation may be performed to report information to theserver, but also the second predetermined operation may be performed formaking a maintenance processing timely. For example, when a terminaldevice cannot operate normally due to a failure, the terminal deviceexecutes by itself a second predetermined operation sent from the serverto make a failure repair and data backup for the terminal in addition toexecuting a first predetermined operation to report data to the devicemanagement server, instead of simply reporting information by a DM agentmodule on the terminal device to the DM server as in the prior art.

A predetermined operation may be presented on the management tree of thedevice in the following five approaches.

1. Executable Node

The second predetermined operation sent from the DM server may bedirectly attached to the management tree in a form of an executablenode. As shown in FIG. 3A, the leaf node Action is defined as the secondpredetermined operation sent from the DM server. This leaf node Actionis directly attached to the management tree as an executable node, andmay be directly executed by an Exec command to perform an operation uponthe occurrence of the trigger condition. An example of the Exec commandis illustrated as follows.

  <Exec>     <CmdID>2</CmdID>     <Item>      <Target>       <LocURI>/MalFunction/Action </LocURI><!-- Enable triggering andexecuting the action upon occurrence of a failure -->  </Target>   </Item>  </Exec>

2. Path Name

The path name of an executable script file for the second predeterminedoperation is stored on the management tree as a value of a leaf node.The DM agent executes the file indicated by the path name upon theoccurrence of the trigger condition. As shown in FIG. 3B, the leaf nodePath in the Trap MO structure stores the path name of a script file forthe second predetermined operation. When the trigger condition occurs,the DM agent reads the path name of the script file for the secondpredetermined operation and executes the script file with an Execcommand, thus implementing the trigger mechanism. An example of the Execcommand is illustrated as follows.

  <Exec>     <CmdID>2</CmdID>     <Item>        <Target>         <LocURI>/MalFunction/Path </LocURI><!-- Enable triggering andexecuting the action upon occurrence of a failure -->       </Target>   </Item>  </Exec>

3. Textual Information in Extensible Markup Language (XML) Stored in aNode

The second predetermined operation sent from the DM server may bedirectly stored in a node in a form of XML textual information. Thisoperation may be sent to the management tree along with a Trap by the DMserver, and may be executed by executing the value of the node with anExec command upon the occurrence of the trigger condition. Thisconstruction is shown in FIG. 3C. When the trigger condition occurs, thesecond predetermined operation is executed through making an XML parsingon the value of the leaf node Operation.

If the XML description of the predetermined operation is executed withan Exec command upon the occurrence of the trigger condition, theattributes of the Operation node are illustrated as follows.

Tree Occurrence Format Min. Access Right Zero Or More CData Get, Exec

4. Uniform Resource Identifier (URI) Stored in a Node

The second predetermined operation sent from the DM server may bedirectly stored in a node in a form of a URI. This operation may be sentto the management tree along with a Trap by the DM server, and may beexecuted by executing the value of the node with an Exec command uponthe occurrence of the trigger condition. This construction is shown inFIG. 3D. When the trigger condition occurs, the second predeterminedoperation is retrieved by means of the value of the leaf node Operationindicating the operation and then is executed.

For the construction in FIG. 3D, the Operation node stores thepredetermined operation to be executed upon the occurrence of thetrigger condition, and has a format as follows.

Tree Occurrence Format Min. Access Types Zero Or More chr Get

If the value of the Operation node is ./ABC/Action, it indicates thatwhen the trigger condition is satisfied, a predetermined operationindicated by the URI will be triggered to implement the task sent inadvance by the DM server. The corresponding command is illustrated asfollows.

 <MgmtTree>   <Node>    <NodeName>.</NodeName>   <DFProperties>...</DFProperties>    <Node>    <NodeName>Trap</NodeName>     <DFProperties>...</DFProperties>    <Node>      <NodeName>Operation</NodeName>     <DFProperties>...</DFProperties>      <Value>./ABC/Action</Value>-- the value of the node, which indicates the predetermined operation tobe executed when the trigger condition is satisfied --     </Node>   </Node>   </Node>  </MgmtTree>

5. Unique Predetermined Operation Identifier Stored in a Node

The second predetermined operation sent by the DM server may be directlystored in a node in a form of a unique predetermined operationidentifier. This operation may be sent to the management tree along witha Trap by the DM server. Each predetermined operation corresponds to aunique predetermined operation identifier. The DM server associates thetrigger condition with the unique predetermined operation identifier ofthe predetermined operation. In this way, the terminal device maytrigger the predetermined operation sent from the DM server by means ofthe unique predetermined operation identifier when the trigger conditionoccurs. This construction is shown in FIG. 3E. When the triggercondition occurs, the second predetermined operation is retrieved bymeans of the value of the leaf node Operation indicating the operationand then is executed.

With reference to FIG. 3E, the node ./ABC/Action1/Action ID denotes aunique predetermined operation identifier identifying a predeterminedoperation. Each predetermined operation corresponds to a uniquepredetermined operation identifier. The corresponding command isillustrated as follows.

 <MgmtTree>   <Node>    <NodeName>.</NodeName>   <DFProperties>...</DFProperties>    <Node>    <NodeName>ABC</NodeName>     <DFProperties>...</DFProperties>    <Node>      <NodeName>Action1</NodeName>     <DFProperties>...</DFProperties>      <Node>      <NodeName>ActionID</NodeName>      <DFProperties>...</DFProperties>       <Value>1234</Value> -- thevalue of the node, which indicates the unique identifier identifying thepredetermined operation to be executed when the trigger condition issatisfied --      </Node>     </Node>    </Node>   </Node>  </MgmtTree>

The above XML description shows that those predetermined operations aredistinguished from each other by a unique identifier, for example, 1234in the above example.

 <MgmtTree>   <Node>    <NodeName>.</NodeName>   <DFProperties>...</DFProperties>    <Node>    <NodeName>Trap</NodeName>     <DFProperties>...</DFProperties>    <Node>      <NodeName>Operation</NodeName>     <DFProperties>...</DFProperties>      <Value>1234</Value> -- thevalue of the node, which indicates the unique identifier identifying thepredetermined operation to be executed when the trigger condition issatisfied --     </Node>    </Node>   </Node>  </MgmtTree>

The Operation node in the Trap MO stores a unique identifier identifyinga predetermined operation to be executed when the trigger condition issatisfied. With this unique identifier, the client may execute thepredetermined operation sent from the server when the trigger conditionis satisfied.

The predetermined operations may be managed on the terminal device inthe construction approaches as below.

1. To extend functions for the trigger mechanism without a big change inthe existing Trap MO, an executable node defining the secondpredetermined operation, for example an executable node Action, may beadded to the existing Trap MO, so that the DM agent may be triggered toexecute the second determined operation upon the occurrence of thetrigger condition. The structure of the Trap MO is shown in FIG. 4A, inwhich the Action node denotes the second predetermined operation to beexecuted by the DM agent upon the occurrence of a fault event. Theposition at which the Action node is attached to the Trap MO is notlimited to that shown in FIG. 4A. In this way, the function that onlyincludes reporting diagnostic results or fault reports is extended forthe Trap MO. The DM agent may also send diagnostic data or faulttracking reports to the DM server while executing the secondpredetermined operation sent from the DM server, but is not limited tothis by extension. When the leaf node Result is empty, the DM agent doesnot send diagnostic data or fault tracking reports to the DM server. Inother words, the construction approach means that the secondpredetermined operation may be presented in the Trap MO as an executablenode.

For example, when the trigger condition occurs, the Action operation maybe triggered and executed with an Exec command. An example of the Execcommand is illustrated as follows.

 <Exec>   <CmdID>2</CmdID>   <Item>     <Target>      <LocURI>/MalFunction/Action </LocURI><!-- Enable triggering andexecuting the action upon occurrence of a failure -->     </Target>  </Item>  </Exec>

2. For not changing the structure of the existing Trap MO, an MOstructure as shown in FIG. 4B may be utilized to manage the secondpredetermined operation.

In FIG. 4B, the ActionManager node is attached to the management tree ofthe terminal device as an interior node.

The leaf node Firepoint stores a TrapID corresponding to a triggercondition. When the trigger condition is satisfied and an execution of asecond predetermined operation sent from the DM server is triggered, theTrapID corresponding to the trigger condition is stored to the leaf nodeFirepoint.

The leaf node ActionManager/<X>*/TrapID stores a TrapID of a triggercondition. This TrapID corresponds to the TrapID in the Trap MO.

The leaf node ActionManager/<X>*/Action describes the secondpredetermined operation. This node may be an executable node (as statedabove) which may be directly executed by an Exec command.

Through this central management mechanism for triggering operations,when a trigger condition occurs, its TrapID is stored to the Firepointnode. By monitoring the Firepoint node and checking whether the value ofthe TrapID node under the ActionManager node is identical to the valueof the Firepoint node, it is determined whether to execute thepredetermined operations from DM Server corresponding to the triggerconditions. In other words, this construction approach means that thesecond predetermined operation is presented in a form of a treestructure or executable node and is associated with the Trap MO in theterminal device with a predefined association identifier, and the secondpredetermined operation and the association identifier belong to thesame parent node. The predefined association identifier is the uniqueidentifier TrapID of the Trap MO in the terminal device.

3. For not changing the structure of the existing Trap MO, an MOstructure as shown in FIG. 4C may be utilized to manage the secondpredetermined operation.

With reference to FIG. 4C, a node for storing a TrapID may be added tothe MO for the second predetermined operation. A TrapID denotes anassociated Trap MO. In this way, an association is established betweenthe second predetermined operation and the Trap MO. By means of thisassociation, the Trap agent notifies the terminal device to execute asecond predetermined operation associated with the TrapID when thetrigger condition is satisfied.

In other words, this construction approach means that the secondpredetermined operation is presented in a form of a tree structure andis associated with the Trap MO in the terminal device by means of apredefined association identifier, and the association identifier islocated in a node on the tree where the second predetermined operationresides. The predefined association identifier is the unique identifierTrapID of the Trap MO in the terminal device.

With reference to FIG. 5, a procedure for processing a faultevent-triggered predetermined operation is described as follows.

In process 1, the DM server delivers an event-triggered diagnosing orfault tracking operation in a form of a Trap MO, and delivers a failurerecovery operation (or a data backup operation or other operations) atthe same time.

In process 2, the DM agent in the terminal device monitors fault eventsand collects diagnostic data or fault reports.

In process 3, the fault-triggered event occurs and the terminal cannotoperate normally due to a failure, the DM agent executes the triggeredoperation and reports the fault reports on this failure to the DMserver.

In process 4, the DM agent executes the failure recovery operationdelivered by the DM server and sends a result of the operation to the DMserver.

With reference to FIG. 6, a procedure for processing a time-triggeredpredetermined operation is described as below.

In process 1, the DM server delivers a time-triggered action and a databackup operation.

In process 2, the DM agent in the terminal device detects whether thetime trigger condition is satisfied.

In process 3, the time trigger condition is satisfied and the DM agentexecutes the action, for example, reports the data to the DM server.

In process 4, the DM agent executes a data backup operation and sends aresult of the execution of the backup operation to the DM server.

In the above two procedures, there may be only the second predeterminedoperation, that is, there may be only the failure recovery operation orthe data backup operation.

A particular example for implementing the present invention is describedas below.

In an operator's network, there are provided a plurality of WirelessApplication Protocol (WAP) gateway addresses. If one WAP server addressis unable to be accessed, a user who has set this WAP server addresscannot access the network through WAP. In this case, the WAP gatewayserver address on the user's terminal may be automatically changed by adelivered predetermined operation. The changed server address may be adefault WAP gateway address set by the DM server, and also may beobtained by attempting the other WAP gateway server addresses until onewhich may be accessed normally is found. The changing of the WAP gatewayaddress on the terminal is executed by the predetermined operationdelivered by the DM server.

The server sends a Trap and monitors the WAP accessing in the terminal.When the terminal fails to access the WAP server for two times, apredetermined operation is triggered and executed to automaticallychange the WAP server address into a spare WAP server address which ispreset by the DM server when the Trap is delivered.

A Trap MO delivered by the server has a format as described below.

/*------- <X>/Server/<X>*/ServerID -------*/ <Replace>  <CmdID>1</CmdID> <Item>   <Target>    <LocURI>/FailGw/Server/scts/ServerID</LocURI>  </Target>   <Meta>    <Format xmlns=‘syncml:metinf’>chr</Format>  </Meta>   <Data>com.openmobilealliance.DMServer</Data>  </Item></Replace>

The above XML description indicates the server to which the diagnosticdata or fault reports are reported upon the occurrence of the monitoredevent.

/*------- <X>/Server/<X>*/Enabled -------*/ <Replace>  <CmdID>2</CmdID> <Item>   <Target>    <LocURI>/FailGW/Server/scts/Enabled</LocURI>  </Target>   <Meta>    <Format xmlns=‘syncml:metinf’>bool</Format>  </Meta>   <Data>true</Data>  </Item> </Replace>

The above XML description indicates the condition monitor is enabled.

 /*------- <X>/Server/<X>*/Reporting/Type -------*/   <Replace>  <CmdID>3</CmdID>   <Item>   <Target>  <LocURI>/FailGW/Server/scts/Reporting/Type</LocURI>   </Target>  <Meta>   <Format xmlns=‘syncml:metinf’>chr</Format>   </Meta>  <Data>EV</Data>   </Item>   </Replace>  //This segment of XMLdescription indicates that the trigger condition is an event triggercondition   /*------- <X>/Server/<X>*/Reporting/Value -------*/  <Replace>   <CmdID>3</CmdID>   <Item>   <Target>  <LocURI>/FailGW/Server/scts/Reporting/Value</LocURI>   </Target>  <Meta>   <Format xmlns=‘syncml:metinf’>int</Format>   </Meta>  <Data>2</Data>   </Item>   </Replace>  //This segment of XMLdescription indicates that the predetermined operation is enabled whenthe monitored event has occurred for two times.

When the trigger condition occurs, i.e. the disposition of passingthrough the original WAP gateway is not workable, a second predeterminedoperation as described below is executed to repair the failure. Thedelivered XML description of the second predetermined operation isdescribed as follows.

  <Replace>   <CmdID>4</CmdID>   <Item>   <Target>  <LocURI>./settings/wap_settings/GW</LocURI>   </Target>  <Data>10.0.0.172</Data>   </Item>   </Replace> // This segment of XMLdescription indicates that the original WAP gateway address is changedto be 10.0.0.172 which is a spare address of the WAP gateway of theoperator.

An apparatus for implementing a predetermined operation in devicemanagement is provided in view of the above description. A schematicstructure diagram of the apparatus is shown in FIG. 7. This apparatus islocated in a terminal 710, and includes a predetermined operationreceiving module 711, a storing module 712, a predetermined operationexecuting module 713 and a monitoring module 714.

The predetermined operation receiving module 711 is adapted to receive acondition-triggered second predetermined operation sent by a devicemanagement server 720 and store the condition-triggered secondpredetermined operation into the storing module 712.

The storing module 712 is adapted to store the second predeterminedoperation and a predefined trigger condition.

The monitoring module 714 is adapted to monitor whether the triggercondition is satisfied and notify the predetermined operation executingmodule 713 when the trigger condition is satisfied.

The predetermined operation executing module 713 is adapted to obtainthe second predetermined operation from the storing module 712 andexecuting the obtained second predetermined operation according to thereceived notification.

In addition, the predetermined operation receiving module 711 may befurther adapted to receive a condition-triggered first predeterminedoperation sent from the device management server 720 and store the firstpredetermined operation into the storing module 712.

The storing module 712 may be further adapted to store the firstpredetermined operation.

The predetermined operation executing module 713 may be further adaptedto obtain the first predetermined operation from the storing module 712and execute the obtained first predetermined operation according to thereceived notification.

The second predetermined operation includes maintenance processing to beimplemented locally by the terminal device. The first predeterminedoperation includes reporting diagnostic result and/or fault reports bythe terminal device to the device management server.

In a view from above, the present invention extends the applicationscenarios of the trigger mechanism, thus a predetermined operation sentfrom a server may be executed upon the occurrence of a triggercondition. Especially for the mechanism of Trap MO, the terminal deviceis not limited to reporting information to the server. For example, whenthe device cannot operate normally due to a failure, the terminal devicecan automatically execute a second predetermined operation deliveredfrom the server so as to recover from the failure or make a data backup,instead of simply reporting the failure information or fault informationto the DM server.

It is apparent that a person skilled in the art may make variousmodifications and verifications on the present invention, withoutdeparting from the spirit and scope of the present invention. Thus thepresent invention intends to cover any of those modifications andverifications.

1. A method for implementing a predetermined operation in devicemanagement in a terminal device, being based on a device managementsystem defined by Open Mobile Alliance Device Management Protocol,wherein a device management server sends a first predetermined operationand a trigger condition to the terminal device, the first predeterminedoperation is used for reporting information to the device managementserver, the first predetermined operation and the trigger condition arestored into a Trap management object of a management tree of theterminal device, and the first predetermined operation is executed bythe terminal device when the trigger condition is satisfied, wherein themethod comprises: receiving, by the terminal device, a secondpredetermined operation and a uniform resource identifier of the secondpredetermined operation sent by the device management server; storing,by the terminal device, the uniform resource identifier of the receivedsecond predetermined operation into the Trap management object, andstoring the second predetermined operation into the management treeoutside of the Trap management object; and when the trigger condition issatisfied, reading the uniform resource identifier from the Trapmanagement object and obtaining the second predetermined operationcorresponding to the uniform resource identifier from the managementtree of the terminal device, and executing the second predeterminedoperation.
 2. The method according to claim 1, wherein the secondpredetermined operation comprises maintenance processing to beimplemented.
 3. The method according to claim 2, wherein the maintenanceprocessing comprises failure repair and/or data backup.
 4. The methodaccording to claim 1, further comprising reporting a result of thesecond predetermined operation to the device management server afterexecuting the second predetermined operation.
 5. The method according toclaim 1, wherein the first predetermined operation comprises reportingdiagnostic and/or fault information to the device management server. 6.An apparatus for implementing a predetermined operation in devicemanagement based on the Open Mobile Alliance Device Management Protocol,being applicable to a terminal device, wherein the apparatus comprises apredetermined operation receiving module adapted to receive a firstpredetermined operation and a trigger condition sent from a devicemanagement server, the first predetermined operation used for reportinginformation to the device management server when the trigger conditionis satisfied, a storing module adapted to store the first predeterminedoperation and the trigger condition into a Trap management object of amanagement tree of the terminal device, a predetermined operationexecuting module adapted to obtain the first predetermined operationfrom the storing module and to execute the obtained first predeterminedoperation according to a received notification, and a monitoring module,wherein: the predetermined operation receiving module is further adaptedto receive a second predetermined operation and a uniform resourceidentifier of the second predetermined operation, sent by the devicemanagement server; the storing module is further adapted to store theuniform resource identifier of the received second predeterminedoperation and the trigger condition into the Trap management object andstore the second predetermined operation into the management treeoutside of the Trap management object; the monitoring module is adaptedto monitor whether the trigger condition is satisfied and to notify thepredetermined operation executing module when the trigger condition issatisfied; and the predetermined operation executing module is furtheradapted to read the uniform resource identifier from the Trap managementobject and obtain the second predetermined operation corresponding tothe uniform resource identifier, and then to execute the secondpredetermined operation, according to the received notification from themonitoring module.